Multi-modal method for interacting with 3d models

ABSTRACT

The present disclosure concerns a methodology that allows a user to “orbit” around a model on a specific axis of rotation and view an orthographic floor plan of the model. A user may view and “walk through” the model while staying at a specific height above the ground with smooth transitions between orbiting, floor plan, and walking modes.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of pending U.S. patent application Ser. No. 15/722,269, filed on Oct. 2, 2017, entitled “MULTI-MODAL METHOD FOR INTERACTING WITH 3D MODELS”, and now issued as U.S. Pat. No. ______, which is a continuation of U.S. patent application Ser. No. 13/925,772, filed on Jun. 24, 2013, entitled “MULTI-MODAL METHOD FOR INTERACTING WITH 3D MODELS”, and now issued as U.S. Pat. No. 9,786,097, which claims the benefit of U.S. Provisional Application No. 61/663,265 filed Jun. 22, 2012, entitled “WEB PLAYER FOR VIEWING MODELS”. The entireties of the aforementioned applications are hereby incorporated herein by reference.

BACKGROUND Field of the Invention

The present invention generally related to three-dimensional (3D) modeling. More specifically, the present invention relates to a methodology that allows a user to “orbit” around a model on a specific axis of rotation and view an orthographic floor plan of the model. The present invention further allows a user to view and “walk through” the model while staying at a specific height above the ground with smooth transitions between orbiting, floor plan, and walking modes.

Description of the Related Art

There has been extensive work in the field of interactive, first-person 3D immersive environments in which users are able to walk through a virtual space. The last quarter-century of first-person shooter video games are evidence of and otherwise exemplary of the same.

Complementing and expanding upon this work are various tools for visualizing 3D models of terrain. Aerial modeling tools such as Google Earth allow users to virtually explore urban areas in 3D from an aerial point of view. Panoramic modeling tools such as Google Street View allow users to view multiple 360-degree panoramas of an environment and to navigate between these multiple panoramas with a visually blended interpolation. Finally, there exist a more generally applicable variety of 3D modeling tools such as Maya® 3D animation software and 3ds Max® software that allow users to view 3D models in an object-centric manner whereby a user may zoom in and out on the model and rotate the same around a desired central point.

It is also becoming more feasible to automatically capture real-world spaces in 3D. These captured spaces may then be converted into 3D models. Exemplary tools for such capture include laser scanners, coordinate measuring technologies, and various software suites from FARO Technologies and the 3D capture system from Matterport.

With these developments, there is a consequential need to view and navigate these 3D models on an array of computing devices.

SUMMARY OF THE PRESENTLY CLAIMED INVENTION

A first claimed embodiment encompasses a system for three-dimensional modeling. The system includes an input device that receives user interactions, a storage device, and an output device. The storage device includes instructions that are executable by a processor to generate, manipulate, or update three-dimensional modeling data. The output device displays the three-dimensional modeling data.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a high-level block diagram for interacting with a 3D model.

FIG. 2 illustrates a detailed workflow for certain processing steps that might take place in the context of FIG. 1.

FIG. 3 illustrates an exemplary computing device for implementing the 3D modeling interactions disclosed herein.

DETAILED DESCRIPTION

Disclosed herein is a methodology that allows a user to “orbit” around a model on a specific axis of rotation and view an orthographic floor plan of the model. The present invention further allows a user to view and “walk through” the model while staying at a specific height above the ground with smooth transitions between orbiting, floor plan, and walking modes. Exemplary and non-limiting use cases include documentation of buildings for insurance, advertising of spaces online for real estate, and space modification for redecoration and remodeling. The foregoing use cases benefit from a mix of modes for navigating a space, including walking inside the space, orbiting the space from above, and viewing a floor plan of the space.

These methodologies may utilize computing hardware that is capable of processing and rendering 3D graphics, a display for showing the 3D model, and any number of input devices for receiving and processing user input. The computing hardware may contain special processing capability for 3D graphics such as a graphics processing unit (GPU).

A variety of input devices are envisioned, including buttons on a joystick or mouse, keys on a keyboard, or virtual touchscreen buttons. Such button inputs may be shown on a display and utilized to trigger a transition between target modes as will be described further herein. Various button inputs may also be used to move and/or rotate a camera. While described as buttons, such inputs may utilize any variety of icons or symbols such as arrows, increase/decrease (+/−) slide bars, and ‘virtual hands.’ Alternately, inputs that provide positional data such as a mouse, analog joystick, touchscreen, or gesture input devices and associated hardware and/or software may be used.

User input and information about the 3D model being displayed is used to update the position of a virtual camera used by a 3D rendering engine to render the 3D model. One of ordinary skill in the art will appreciate that various references to engines, modules, or executable software in general envision the embodiment of computer-readable instructions in a non-transitory computer readable storage medium. Those instructions may then be executed by a processor or array of processors in any variety of steps, series, or orders in an effort to implement the various functionalities, methodologies, and processes described herein. The foregoing is not meant to exclude—and, in fact, specifically includes—the possibility of application specific processors or dedicated computing hardware to perform certain steps or operations as may be appropriate in certain contexts or to enjoy certain efficiencies.

3D models may come in a variety of formats. Models may include one or more meshes of triangles, quads, and/or n-gons. 3D models may also include curved surfaces such as non-uniform rational basis splines (NURBS), which are a function of two parameters mapped to a common surface area in three-dimensional space. Models may also have associated color or material properties. For example, each vertex of a mesh may contain associated texture data in one or more separate images via UV mapping. Examples of common 3D model formats include “.obj”, “.fbx”, and “.dae.”

3D models may contain metadata, some of which may be tied to specific sets of coordinates. This metadata may contain a name for the model, information about when, where, by whom, and with what hardware, the model was captured. The metadata may also contain annotations tied to specific locations, areas, or volumes on or around the model, as well as measurements of dimensions on or around the model.

A 3D model may be captured from a real-world location. The model dimensions may thus match the real-world dimensions of the location.

The 3D model may be locally stored in memory present on or coupled to the computing device. The 3D model may also be downloaded from a remote location by the modeling software in conjunction with a wired or wireless network connection and associated network hardware (e.g., wireless processor or Ethernet port). The software may allow the user to browse a list of 3D models available for viewing. The list may reflect models already downloaded and/or available for download. 3D models may also be streamed such that they may be loaded and rendered in part or at reduced resolution prior to the downloading of the full model.

FIG. 1 illustrates a high-level block diagram for interacting with a 3D model. Step 101 of FIG. 1 reflects the collection of user input. Step 102 of FIG. 1 reflects updating of an internal model (103). The user input from step 101 as well as information from internal model 103 may be used to update the internal model 103. Step 102 of FIG. 1 may run in a loop thereby continuously updating internal model 103 as well as processing any user input that may be received as a part of step 101.

Internal model 103, which may be stored locally in memory, in cloud storage, or downloaded from cloud storage in part of in whole, may include a variety of information. First, internal model 103 may include information about a virtual camera used as a viewpoint for rendering the 3D model. This may include the position, orientation, field of view, and type of perspective for the camera. It may also contain information that is used to update camera position, such as current velocity or rate of rotation, as well as the current mode of user interaction.

Rendering update loop (step 104) takes the information from internal model 103, including camera information, and generates a 3D rendering of the 3D object for display in step 105. A variety of 3D rendering engines for rendering 3D models are known in the art and may be implemented in the context of step 104.

Rendering update loop 104 may execute partially or entirely on a GPU. Update loop 104 may likewise execute in a massively parallel processing section of a heterogeneous processor architecture. The update loops of steps 102 and 104 may run on the computing device in an alternating or multithreaded manner, and access to internal model 103 may be locked to ensure that loops 102 and 104 are not interacting with internal model 103 at the same time.

In step 105, data is displayed on a display such as an LCD screen or OLED.

FIG. 2 illustrates a detailed workflow for certain processing steps that might take place in the context of FIG. 1. More specifically, FIG. 2 illustrates in detail processing loops 102 and 104 of FIG. 1 with respect to their interactions with internal model 103. The internal model 103 may include one of four modes: orbit mode 201, floor plan mode 205, transition mode 213, and walking mode 209. Further modes are within the scope of the present invention. The update loops (202, 206, 210, 214) of the foregoing modes may, in some embodiments, be handled by a single loop with behavior that branches or otherwise differs depending on the mode. Other implementations are, however, possible and not meant to be limiting.

The update loops of orbit, floor plan, transition, and walking mode (202, 206, 214, and 210) may involve making changes to internal model 103 based on current parameters for camera movement. These changes may depend on the amount of time that has passed since the last iteration of the update loop. For example, if a camera parameter is changing at a specific rate, then the corresponding parameter value may be changed by the rate multiplied by the amount of time that has passed since the last iteration of the update loop.

These four update loops (202, 206, 210, and 214) may detect user input events (203, 207, 211, and 215, respectively), which may trigger a variety of actions. In some cases, the user input event for the corresponding mode or modes may lead to a new desired set of camera parameters such as position or orientation. These new camera parameters will, in turn, involve recalculating the corresponding internal model of camera parameters (204, 208, 212, 216). In other cases, the user input event may trigger a transition to a new target mode 216 as discussed in further detail below.

Orbit Mode

Multiple types of motion may be possible in orbit mode 201. The position of the camera may be pitched up or down, rotated left or right around a vertical axis, zoomed in or out, or panned horizontally. The pitch, rotation-around-a-vertical-axis, and zoom motions may be relative to a central point. The vertical axis of rotation may pass through the central point. In the case of pitch and rotation-around-a-vertical-axis, those motions maintain a constant distance to the central point. Thus, the pitch and rotation-around-a-vertical-axis motions of the camera may be thought of as vertical and horizontal travel, respectively, on the surface of a sphere centered on the central point. Zoom may be thought of as travel along the ray defined as passing through the camera to the central point.

The point on the 3D model with or without back-face culling or other ceiling removal techniques that is rendered in the center of the display may be used as the central point. Alternately, this central point may be defined by the point of a horizontal plane that is at the center of the display. This horizontal plane may be invisible, and its height may be defined by a global height of the floor of the 3D model. Alternately, a local floor height may be determined, and the intersection of the ray cast from the camera to the center of the display with the surface of the local floor height may be used to determine the central point.

The height of the floor of the 3D model may be determined via a variety of methods. For example, the points or faces of the model with normal vectors that are within a particular threshold angle of vertical pointing up may be assumed to be candidate floor locations. A global floor height could be calculated by determining the median of the heights of these candidate floor locations. Alternately, a local floor height could be computed by taking the average or median of floor heights over a specific area.

In an embodiment of orbit mode, the projection mode for the 3D rendering is perspective mode. The orientation of the camera may disallow rolling such that the view of the model is never tilted to one side. Limitations on these and other possible modes, orientations, and positions may be imposed. For example, pitch may be clamped such that it is impossible to go past 90 degrees down at the steepest or some angle above 0 degrees down at the shallowest. The zoom level may be clamped such that the closest zoom is a specified distance from the central point and the farthest zoom is such that the entire 3D model is visible.

Users may use either button-based input (e.g., keys) or position-based input (e.g., mouse or touchscreen) to move the camera relative to the model. These input events 203 may trigger a change in orbit mode camera parameters (204). A position-based user input controller may control the position of the camera along horizontal coordinates. For example, the X and Y coordinates of the user input controller may control the X and Y coordinates of a central point linked to the 3D model on the display. For reference, the X and Y coordinates of the model refer to the two horizontal dimensions and the Z coordinate refers to the vertical dimension.

The amounts of motion may be linked to provide the appearance of dragging the model. As a user moves their finger on a touchscreen or a mouse cursor over the model, the central point under the finger or cursor stays under the finger or cursor as the camera is being dragged relative to the model. The controller for this input may be, for example, dragging a single finger on a touchscreen, or left-clicking and dragging with a mouse.

Another position-based input may be used to control pitch and rotation-around-a-vertical-axis. For example, the X and Y coordinates of the user input controller may control the pitch and rotation-around-a-vertical-axis angles, respectively. Leftward motion may rotate the camera counter-clockwise around a vertical axis while upward motion may pitch the camera down. The controller for this input may be, for example, dragging two fingers on a touchscreen, or right-clicking and dragging with a mouse. In an alternate configuration, the rotation of the angle and change in the distance between two fingers in a multi-touch or gesture input may be used to control the rotation-around-a-vertical-axis and zoom of the camera, respectively. In a still further configuration, the position of the centroid of two fingers may be used to control the position of the camera along horizontal coordinates using the various methods described herein. Motion of a mouse scroll wheel may also be mapped to the zoom functionality. The vertical position of the centroid of a two- or three-finger multi-touch gesture may be used to control pitch.

Button-based controls may be used to directly control the various camera motions, including pitching, rotating around a vertical axis, and zooming, and horizontal movement over the surface of the model. For example, on a keyboard, the up and down arrow keys may pitch the camera down and up, respectively, while the left and right arrow keys will rotate the camera around a vertical axis clockwise and counterclockwise, respectively. The “+” and “−” keys may zoom the camera closer to and further away from the model, respectively. The “W,”“A,” “S,” and “D” keys or the up, left, down, and right arrow keys may move the camera forward, left, backward, and right along the horizontal plane, respectively. The foregoing key pairings are exemplary; alternative key pairing configurations are possible.

The detection of user input, as well as the updating of camera position and orientation based on current velocity and rate of rotation, may occur as part of update loop 202. A user input event 203 may trigger recalculation of camera parameters 204 or a transition to another mode 216. Once camera parameters are recalculated 204, update loop 202 may update them as processor bandwidth allows or is otherwise allocated and scheduled.

Floor Plan Mode

In floor plan mode 205, the 3D model is viewed from above with the camera facing straight down at an approximately 90 degree angle. In one embodiment of floor plan mode, the projection mode for the 3D rendering is orthographic, thereby creating a floor plan-like appearance for the model.

The set of input controls and mappings in floor plan mode may be a subset of those for orbit mode. For example, the controls for floor plan mode may be identical to those described in the context of orbit mode with the exception that the pitch is clamped at 90 degrees downward. Rotation about a central point along a vertical axis is still possible as is zooming in and out toward and away from that point and moving the central point. The model may, however, only be viewed directly from above as a result of the clamping of pitch at 90 degrees. When the camera is pointing straight down in floor plane mode, the rotation of the camera relative to a vertical axis is a roll motion of the camera itself.

The zoom control in floor plan mode may be set differently from that of orbit mode. Since the camera projection may be orthographic, the area of model that is viewed may be changed when the user zooms in or out. Zooming in may decrease the area viewed while zooming out may increase the area viewed.

The detection of user input, as well as the updating of camera position and orientation based on current velocity and rate of rotation, may occur as part of floor plan mode update loop 205. A user input event 207 may trigger recalculation of camera parameters 208 or a transition to another mode 216. Once camera parameters are recalculated 208, update loop 206 may update those parameters in a manner similar to that of update loop 202 in orbit mode and as described above.

Walking Mode

In Walking Mode 209, users navigate the surface of the model with a navigation metaphor similar to the experience of walking on an exterior or interior surface of the model itself. In one embodiment, the camera stays at a fixed height above either the surface of the model or a locally or globally determined floor height by default. In another embodiment, the user in the virtual space of the 3D model may be defined as a particular volume. For example, the volume may be defined as a capsule shape with the axis of symmetry oriented along the Z axis. The camera may be designated to have a locale that is specific but nevertheless relative to the pre-defined volume. As a result, the position of the camera is determined by the interaction of the user volume with the 3D model. A downward gravity direction (and thus a definition of “up”) may be defined as a vector pointing in the negative direction for the Z axis.

A collision checking mechanism may be implemented in some embodiments in order to prevent the camera or user volume from passing through the boundaries of the model. A physics engine may be used to allow the user volume to move in realistic ways through the 3D model. Multiple commercial and open-source 3D game engine packages provide this collision-checking and physics functionality off-the-shelf, including but not limited to the Unity Technologies Unity game engine, the Unreal Engine from Epic Games, Inc., and the CryENGINE® from CRYTEK. The physics engine, collision checking, and/or 3D game engine may run within, concurrently to, or in sequence with, update loop 210.

A “crouch” functionality may also be implemented thereby allowing the user to lower the height of the camera as well as possibly reduce the height of the user volume. A corresponding “jump” functionality may give the user a vertical velocity thereby propelling them upward. The physics engine may apply a negative vertical acceleration to pull the user back downward in a physically realistic manner as well as realistically handle the user walking off the edge of a surface.

Input events 211 may be used to trigger camera rotation, camera movement, jumping, crouching, a transition to a new mode, or other behaviors. The camera parameters may be recalculated using this input event 211 in step 212 of FIG. 2.

Users may use either button-based input such as keys or position-based input such as a mouse or touchscreen to move the camera around the model in walking mode. Position-based input may be used to allow the user to look around and rotate the camera while keeping the position of the camera constant. For example, the X and Y coordinates of the user input controller may control the rotation of the camera relative to a vertical axis passing through the camera and the pitch of the camera, respectively. Similarly, moving the user input controller up, down, left, or right may cause the camera to move up, down, left, or right, respectively.

This mapping may also be reversed such that moving the user input controller up, down, left, or right may cause the camera to move down, up, right, or left, respectively. In such a mapping configuration, the amounts of rotation may be matched to provide the appearance of dragging the model. As a user moves their finger on a touchscreen or a mouse cursor over the model, the point of the model under the finger or cursor may stay under the finger or cursor as the rotation of the camera is dragged relative to the model. Exemplary controllers for this input include dragging a single finger on a touchscreen, or left-clicking and dragging with a mouse.

Position-based input may also be used to move the camera around the 3D model. For example, the Y axis of the input controller may be mapped to forward/back motion and the X axis of the input controller may be mapped to rotation. Upward controller motion may move the camera forward along its central axis, while downward controller motion may move the camera backward along its central axis. Leftward controller motion may rotate the camera relative to a vertical axis passing through the camera to the left while rightward controller motion may rotate the camera along the same axis to the right. Alternately, the X axis of the input controller may be mapped to strafing motion such that leftward controller motion may move the camera to the left while rightward controller motion may move the camera to the right. The controller for this input may be, for example, dragging two fingers on a touchscreen, or right-clicking and dragging with a mouse.

Alternately, the model for moving through the space may be akin to dragging the model. As a user moves their finger on a touchscreen or a mouse cursor over the model, the point of the model under the finger or cursor stays under the finger or cursor as the position of the camera is dragged relative to the model as rotation is held constant.

Button-based controls may be used to directly control the various camera motions, including walking and rotation (pitching and rotation-around-a-vertical-axis). For example, on a keyboard, the up and down arrow keys may move the camera forward and back respectively; the left and right arrow keys may rotate the camera counterclockwise and clockwise around a vertical axis, respectively. The speed of movement may likewise be controllable by, for example, holding down a particular button to increase the rate of movement and rotation or holding down another particular button to decrease the rate of movement and rotation. Holding down the “shift” key and then pressing the up, down, left, or right arrow keys may pitch the camera up, pitch the camera down, rotate the camera clockwise around a vertical axis, and rotate the camera counterclockwise around a vertical axis, respectively. Crouch and jump functionality as previously discussed may be mapped to particular buttons. The scroll wheel of a mouse may be used as an alternate input for forward and backward camera motion.

The detection of user input, the updating of camera position and orientation based on current velocity and rate of rotation, as well as the general operation of a physics engine and a boundary collision checking system may all occur as part of walking mode update loop 210. A user input event 211 may trigger recalculation of camera parameters 212. Input even 211 may also effectuate a transition to another mode 216.

Transition Mode

Transition mode 213 provides a smooth visual transition from one mode to another. During this transition, the camera parameters for orientation and position, as well as other parameters in the internal model 103, are smoothly transitioned from their current initial values to a desired set of target values. The transition may take place over a specified time interval, which may vary depending on the total distance to be traveled during the transition such that longer transitions take more time.

Transitions may be triggered by the user. For example, the user may press a specific button to transition to a specific mode. For transitions from orbit mode or floor plan mode to walking mode, users may trigger a transition by zooming in past the maximum zoom-in level allowed in these modes. A brief delay may be introduced when maximum zoom-in is achieved prior to allowing further zoom-in inputs in order to prevent accidental mode transitions. For transitions from walking mode to orbit mode or floor plan mode, users may trigger a transition by using a button, positional, or gesture input linked to zooming out.

If a transition is triggered, a desired target mode as well as a desired target position and orientation for the camera will need to be determined (216). In a transition between orbit mode and floor plan mode, for example, the central point (as found using one of the methods described herein) at the center of the display may remain the central point in the target position and orientation of the camera. For the transition from orbit mode to floor plan mode, the target position of the camera may be set to be directly above the central point with pitch set to 90 degrees straight down. Since floor plan mode is preferentially rendered in orthographic mode, this transition may be handled by increasing the distance of the camera from the model toward a near-infinite distance while simultaneously narrowing its field of view such that the total portion of the 3D model that remains visible stays relatively constant. For the transition from floor plan mode to orbit mode, the target camera pitch may be either chosen from a preset value (e.g., 45 degrees downward) or chosen from the last pitch value from the last time the user was in orbit mode.

During transitions from either orbit mode or floor plan mode to walking mode, a desired position for the camera near the surface of the model is chosen; this position may be chosen be the user. The user may use a positional input device to touch the desired section of the model to which they desire to transition. A user may use a mouse cursor to double-click on the desired location or the user may use a touchscreen to tap the desired location. This location on the model may then be determined via ray casting. Alternately, the user may simply elect to change to walking mode without specifying a location. In such a case, the location will be automatically determined without further user intervention or interaction. The central point or the part of the 3D model at the center of the display may be used as this automatically determined location. The camera may then be placed at a specified height above this location. If a user volume is being used, the bottom of the user volume may be placed at the local floor height at that location.

The location on the 3D model chosen as the desired position may, in some instances, be inconvenient or impossible to use due to a collision between the 3D model and the user volume. Presence of an object or wall, or the lack of a floor in a particular area may similarly present a positioning difficulty or impossibility. In such a case, an algorithm for finding a viable nearby alternative location may be utilized. One such algorithm would attempt to place a user volume with its bottom at a local floor height at a range of points along a series of successively larger circles surrounding the initial desired position. The first location for which the user volume no longer collides with the 3D model or such collision can be fixed with a small motion may be chosen as the revised target position.

In an embodiment concerning the transition from orbit mode or floor plan mode to walking mode, the target heading (rotation around a vertical axis) of the camera is unchanged while the target pitch of the camera is set to a preset value such as 0. As a result, the target orientation of the user is looking toward the horizon.

For a transition from walking mode to orbit mode, a desired camera position and orientation may be chosen. One option is to return the camera position and orientation to a default “home” configuration. This “home” configuration may be chosen such that the entire 3D model is visible. Alternately, the target camera position and orientation may be chosen such that the camera is pointing down at the location on the 3D model that was directly below the camera prior to the transition and the target camera position is a preset distance from this location. This transformation may make the point on the 3D model under the camera (or the point at the base of the user volume) in walking mode the central point in orbit mode. The heading may be preserved while the pitch may be set either to a fixed value (e.g. 45 degrees down) or the value it had the last time the user was in orbit mode. This set of constraints defines a unique solution to be derived for target camera position and orientation.

For a transition from walking mode to floor plan mode, a desired camera position and orientation may be chosen. One option is to return the camera position and orientation to a default “home” configuration. This “home” configuration may be chosen such that the entire 3D model is visible. Alternately, the target camera position and orientation may be chosen such that it is pointing straight down and positioned directly above the position of the camera prior to the transition. This transformation may make the point on the 3D model under the camera (or the point at the base of the user volume) in walking mode the central point in floor plan mode. The heading may be preserved while the pitch is set to straight down.

Transitions may happen from one camera position in walking mode to a different camera position in walking mode. The user may do this via a particular input such as double-clicking on a mouse or track pad or by double-tapping on a touchscreen. The new location may be computed via a variety of methods. In one method, the part of the 3D model on the location on the screen tapped by the user may be used as a candidate target location for the base of the user volume. It may be impossible to move the user volume to this location. If the user selects, for example, a location on a wall, the user volume associated with the camera may collide with the model in this location. In this case, the methodologies described with respect to a viable location to transition to walking mode from orbit mode may be utilized.

Once a desired target mode and desired target camera parameters are determined, a path for transforming initial camera parameters (i.e., pre-transition parameters) to target parameters (i.e., post-transition parameters) may be computed. The parameters in the projection matrix of the camera may be directly transitioned from the initial projection matrix to the target projection matrix. Alternately, the orientation, position, field of view, and other camera parameters may be transitioned, and new projection matrices may be precalculated or calculated on the fly using these transitional parameters.

Multiple options exist for choosing how the parameters transform from initial values to target values. Linear interpolation is one option, but produces a sudden start and stop. In one embodiment, a formula for an “S” shaped transition is used to provide a smoothly accelerating and decelerating interpolation between two values. One example of such a function is:

f(x)=(1−cos (pi*x))/2

for 0⇐x⇐1

To interpolate parameter value x at time t between an initial parameter value x₁ at transition start time ti and a target parameter value x₂ at transition end time t₂, with “S” shaped transition function f(x) that transitions from 0 to 1 as x goes from 0 to 1, the program may compute it as:

x=x ₁+(x ₂ −x ₁)*f((t−t ₁)/(t ₂ −t ₁))

Updated parameter values may be calculated repeatedly by the transition mode update loop 214 during the specified transition time for all parameters that are transforming from their initial values to their desired target values.

Additional user input events 215 may trigger a new transition. For example, if a user triggers a transition to a specific mode during transition mode, a new target mode with attendant target camera parameters 216 may be determined, and a new transition may begin using the current mid-transition camera parameters as initial camera parameters. Otherwise, position and orientation may not be directly modifiable by the user during transition mode.

Once the target camera position and orientation are determined, the transition mode update loop changes the mode to the target mode (orbit, floor plan, or walking) and the transition period ends.

Input Control Mappings

In all modes (orbit, floor plan, walking, or transition) camera position or orientation may be modified with user input via a positional device such as a mouse, gesture input, or touchscreen. Multiple mapping options exist for the amount of input position change to the output change in the parameter. The mapping may, for example, be position-based whereby the amount of change in input position may directly correlate to the amount of change in the parameter. Alternately, the mapping may be nonlinearly position-based whereby the amount of change in input position raised to a power of greater than 1 may correspond to the amount of change in the parameter. Still further, the mapping may be velocity based whereby the amount of change in input position may set the rate of change in the parameter. Input motions may be damped and/or rate-limited to prevent overly rapid changes in parameters that may be visually jarring to the user. For example, a moving average of the input position over some time interval may be used as input, and the amount or rate of change from the input may be capped at a maximum value.

Rendering

In an embodiment of orbit, floor plan, and transition mode, the rendering process may be modified to allow users to view the inside of the 3D model from a viewpoint outside the 3D model, which may be useful if the model is of an interior space that has a ceiling. Such rendering allows the user to view the interior without the ceiling interfering with model viewing. This may be accomplished by turning on back-face culling in the rendering pipeline.

Alternately, the model may be clipped at a specified height above the floor of the 3D model such that parts of the model above this height are invisible. In another method, the 3D model may be segmented into ceiling areas and non-ceiling areas. Automatic segmentation of the ceiling may be accomplished by first segmenting the walls using, for example, plane detection techniques to detect walls, identifying walls via their vertical orientation and size, and then separating out any parts of the model that are attached to the top of the walls.

In an embodiment of walking mode, the model is not back-face culled nor is it otherwise modified to remove the ceiling. A switch from removing ceilings to not removing ceilings or vice versa may be made at a specified point in the transition during transition mode immediately upon entering or leaving walking mode.

Models may contain multiple floors. For example, the model may be of a multistory building. Viewing lower floors of a multistory model may be difficult in orbit or floor plan modes. The model may be segmented into multiple floors. The user may do this manually by selecting one or more planes to bisect the model by dragging them into the correct location with a vertical motion.

Alternately, multiple floors may be automatically detected via a variety of techniques. For example, candidate floor locations may be identified in the 3D model via the detection of near-vertical upward normal vectors. Then, a floor-dividing plane or surface may then be added slightly below each detected floor height for which there is more than a threshold amount of floor within a specific height interval. Once floor-dividing planes or surfaces are added for each floor, then the user may select a candidate plane or surface above which everything in the 3D model should be hidden in orbit or floor plan mode. These floor selections may be listed as buttons on the display.

Measurement

The method of interacting with the 3D model described herein may allow users to measure dimensions on the model. Users may select start and end locations for the measurement on the model. The computing device may then automatically compute the distance between those two points and display it on the display along with a line between measurement endpoints or other visual representation of the measurement.

The user may select the start and end locations for the measurement using a positional input device such as a mouse, track pad, or touchscreen. In an embodiment, the user first activates a measurement mode using a button press or other input or indicia of choice. The user next uses the positional input device to select a start location for the measurement. The user finally uses the positional input device to select an end location for the measurement. If the user is using a mouse or track pad, the start and end locations may be selected with a click of the mouse button. If the user is using a touchscreen, these locations may be selected by the final position of a touch event. In the event that the user is using a touchscreen, the location of the measurement may be placed slightly above the location of the touch event on the screen and marked on the display with a marker such as a crosshairs. This allows precise placement of measurement points to be made without the points being hidden under the finger of the user. Once the measurement is complete, measurement mode may be automatically deactivated, allowing for normal interaction.

The measurement may be displayed as a line from the measurement start point to the measurement end point. The thickness of the line may taper down to a point at both ends, allowing the precise start and end points to be more clearly viewed. For example, the line may be rendered as three segments—a rectangle along the middle of the line, and a pair of triangles at the endpoints that abut the two short ends of the rectangle.

The distance covered by a measurement may be displayed as text superimposed on the line of the measurement. This text may have a semi-transparent or opaque background surrounding it. As a result, the text may be observed more readily by causing it to be superimposed on the line and 3D model.

A circle or other shape rendered on or near the surface of the 3D model at each endpoint may be rendered during and/or after the measurement process. This may allow users to more precisely place measurements on edges or corners. 3D measurements may be bill-boarded or dynamically oriented so that the lines or polygons making up the measurement line always face the camera.

3D measurements may be rendered in such a way as to ensure that occlusions with the model are clear. For example, each 3D measurement may be rendered as two objects: a first object that is partially transparent and is rendered in front of the 3D model and a second object that is more opaque and is rendered at or near the correct depth thereby allowing closer parts of the 3D model to occlude some or all of the second object.

Alternately, the measurement may be rendered solely at or near the correct depth. The depth of the measurement line may be dynamically moved toward the camera by a small distance with the new endpoint locations possibly staying on the rays from the camera to the true endpoint locations. Such movement may reduce situations in which a bumpy surface partially occludes a measurement line drawn on that surface.

Measurement distances and displayed distance text may update in a continuous fashion as the second endpoint is being placed or an endpoint is being moved. If a user moves an endpoint over a display location for which there is no intersection with a 3D model, the distance text may disappear. The placement of an endpoint at this location may therefore be disabled

A displayed measurement may be selectable by the user, for example, by tapping on the line itself or the measurement text with a positional input device. Once a measurement is selected, additional options may appear on the measurement. For example, a small button may appear on the display near the measurement text allowing the measurement to be deleted. Additionally, buttons at the ends of the measurement line may appear on the display, thereby allowing measurement endpoints to be moved. The movement of endpoints may be accomplished via a click-and-drag motion on a mouse or trackpad, a drag gesture on a touchscreen, or other techniques.

The location on the 3D model for the measurement endpoints may be established via a variety of methods. One such method is raycasting along the vector defined by the camera parameters and the screen coordinates of the desired endpoint. The first intersection with the model may then be identified. Another such method is examining the Z buffer from the rendering to determine the distance to the model at the screen coordinates of the desired endpoint and then projecting from the camera position and orientation to determine the location of this point in three dimensions.

The surface of the 3D model may be analyzed for flat surfaces, edges, and/or corners. Plane detection methods such as the 3D Hough Transform may be used to find the location and orientation of planes in the 3D model. Edges may be determined by a variety of methods. In one method, the faces of the 3D model are segmented into groups that are within a specified distance of a detected plane. The edges of these groups may be defined to be edges of the 3D model. Additionally, edges may be defined as the segments of lines formed by intersections of two detected planes in the 3D model for which there are 3D model faces within a specified distance. Edges of the 3D model may additionally be found by looking for depth differences or ratios between adjacent pixels in the Z buffer of the rendered 3D model that are above a specific amount. Corners may likewise be found by a variety of methods, including the points defined by the intersections of three detected planes in the 3D model.

During the user-guided process of endpoint placement or movement, the interface may snap measurement endpoints to the nearest edge or corner if such an edge or corner is within a specified distance of the current candidate endpoint location with respect to either screen coordinates or 3D world coordinates. The threshold distance for snapping to a corner may be larger than the threshold distance for snapping to an edge.

An additional measurement mode that allows for plane-to-plane or plane-to-point measurements may be available. In this mode, when a user selects a point on the 3D model that is part of a detected plane as a measurement endpoint, the measurement is constrained to the axis of the normal vector of the plane associated with that point.

Measurement may be handled differently in floor plan mode when users desire to make two-dimensional measurements on a horizontal plane. The interface for making measurements in two-dimensions may be similar to the 3D measurement interfaces described herein. The two-dimensional measurement endpoints may, however, be determined by ray casting from the screen location to the horizontal plane or directly mapping the screen coordinates of the endpoints to the world coordinates of the viewed area.

Two-dimensional measurements may also be displayed differently. For example, measurements may be displayed in a “dimension” style with short lines centered at the endpoints that are perpendicular to the line of the measurement. These two-dimensional measurements may be drawn on top of the 3D model such that they are not occluded by the model. In the case of multi-floor models, two-dimensional measurements may be associated with a specific floor. In a particular type of measurement mode, two-dimensional measurements may be snapped to walls or corners, or constrained to be perpendicular to the planes defined by walls using, for example, the plane detection and snapping methods described herein.

When in floor plan mode, 3D measurements made in other modes may be either hidden or visually distinguished from horizontal two-dimensional measurements. For example, such measurements may be distinguished using a different color of line. When in orbit mode or walking mode, horizontal two-dimensional measurements may be hidden, or they may be displayed at a height that is at or a near a local or global floor height.

Annotation

The methods of interacting with the 3D model described herein may allow users to make annotations on the model. To create an annotation, users may first enter annotation mode by pressing an on-screen button or offering other input. Users may then select a location on the 3D model for an annotation using an interface similar to the interface for placing a measurement start point. Users may then type a text string associated with the annotation, or add images or videos (e.g., via drag-and-drop operation) to the annotation. Once the metadata entry is complete, the users may then offer input indicative of finalizing the annotation.

Annotations may be selected, moved, and deleted using interface methods similar to the ones described herein for measurement. Annotation locations may operate in a manner similar to a measurement endpoint. The display area of the annotation data may operate in a manner similar to the measurement text with regard to selection, deletion, and other user operations. Annotation data, 3D measurement data, and two dimensional measurement data may be stored as part of the metadata associated with the 3D model. Thus, measurements and annotations created during a user session may be saved, and measurements and annotations created during prior sessions may be loaded.

FIG. 3 illustrates an exemplary computing device 300 for implementing the 3D modeling interactions disclosed herein. The computing device 300 of FIG. 3 includes one or more processors 310 and memory 320. Main memory 320 stores, in part, instructions and data for execution by processor 310. Main memory 320 can store the executable instructions when in operation. Computing device 300 as shown in FIG. 3 further includes a mass storage device 330, portable storage medium drive(s) 340, output devices 350, user input devices 360, a graphics display 370, and peripheral devices 380.

The components shown in FIG. 3 are depicted as being connected via a single bus 390. The components may, however, be connected through one or more data transport means. For example, processor unit 310 and main memory 320 may be connected via a local microprocessor bus, and the mass storage device 330, peripheral device(s) 380, portable storage device 340, and display system 370 may be connected via one or more input/output (I/O) buses.

Mass storage device 330, which may be implemented with a magnetic disk drive or an optical disk drive, is a non-volatile storage device for storing data and instructions for use by processor unit 310. Mass storage device 330 can store the system software for implementing embodiments of the present invention for purposes of loading that software into main memory 320.

Portable storage device 340 operates in conjunction with a portable non-volatile storage medium to input and output data and computer-readable instructions to and from the computer system 300 of FIG. 3. The computer-readable instructions for implementing embodiments of the present invention may be stored on such a portable medium and input to the computer system 300 via the portable storage device 340 or received by way of a network connection such as those that may be implemented by way of peripherals 380.

Input devices 360 provide a portion of a user interface. Input devices 360 may include an alpha-numeric keypad, such as a keyboard, for inputting alpha-numeric and other information, or a pointing device, such as a mouse, a trackball, stylus, or cursor direction keys. Input devices 360 are also inclusive of network interfaces, which may also operate as an output interface (e.g., an Ethernet connection). Additionally, the system 300 as shown in FIG. 3 includes output devices 350. Examples of suitable output devices include speakers, printers, network interfaces, and monitors.

Display system 370 may include a liquid crystal display (LCD) or other suitable display device. Display system 370 receives textual and graphical information, and processes the information for output to the display device. In some instances, the display system 370 may also offer input and output (e.g., a touchscreen or ‘soft keys’). Peripherals 380 may include any type of computer support device to add additional functionality to the computer system. For example, peripheral device(s) 380 may include a modem or a router or other device offering wireless connectivity. Other peripherals might include additional storage devices or image capture devices.

The components illustrated in FIG. 3 are those typically found in computer systems that may be suitable for use with embodiments of the present invention. The components of FIG. 3 are intended to represent a broad category of such computer components that are well known in the art. The computer system illustrated by way of FIG. 3 may thus be representative of a personal computer, hand held computing device, mobile computing device including any variety of smartphone, tablet computing devices, workstations, servers, as well as any other computing device that might be selected to implement embodiments of the present invention. The computer can also include different bus configurations, networked platforms, multi-processor platforms and implement any variety of suitable operating systems.

The foregoing detailed description has been presented for purposes of illustration and description. It is not intended to be exhaustive or limiting. Modifications and variations are possible in light of the foregoing. The described embodiments sufficiently explain the principles of the technology and its practical application to thereby enable others skilled in the art to best utilize the invention with various modifications. Any limitations as to the present invention are to be defined solely by the scope of the claims appended hereto. 

What is claimed is:
 1. A system, comprising: a processor; and a memory communicatively coupled to the processor, the memory having stored therein computer-executable instructions, comprising: an interface component configured to: generate a graphical user interface that facilitates viewing and navigating a three-dimensional model from different perspectives of a virtual camera in different navigation modes; receive user input indicating a target position of the virtual camera in one of the navigation modes; in response to a determination that a transition from a current position to the target position of the virtual camera collides with the three-dimensional model: select a first position as a new target position, according to an algorithm, such that another transition from the current position to the first position does not collide with the three-dimensional model, and generate at least one representation of the three-dimensional model in the graphical user interface from at least one of the different perspectives based on the new target position.
 2. The system of claim 1, wherein the determination that the transition from the current position to the target position of the virtual camera collides with the three-dimensional model comprises colliding with an object within the three-dimensional model.
 3. The system of claim 1, wherein the determination that the transition from the current position to the target position of the virtual camera collides with the three-dimensional model comprises colliding with a wall within the three-dimensional model.
 4. The system of claim 1, wherein the different navigation modes comprise a walking mode.
 5. The system of claim 1, wherein the different navigation modes comprise an orbit mode.
 6. The system of claim 1, wherein the different navigation modes comprise a floor plan mode.
 7. The system of claim 1, wherein the different navigation modes comprise a transition mode.
 8. A method, comprising: generating, by a system comprising a processor, a graphical user interface that facilitates viewing and navigating a three-dimensional model from different perspectives of a virtual camera in different navigation modes; receiving, by the system, user input indicating a target position of the virtual camera in one of the navigation modes; in response to a determination that a transition from a current position to the target position of the virtual camera collides with the three-dimensional model: selecting, by the system, a first position as a new target position, according to an algorithm, such that another transition from the current position to the first position does not collide with the three-dimensional model, and generating, by the system, at least one representation of the three-dimensional model in the graphical user interface from at least one of the different perspectives based on the new target position.
 9. The method of claim 8, wherein the determination that the transition from the current position to the target position of the virtual camera collides with the three-dimensional model comprises colliding with an object within the three-dimensional model.
 10. The method of claim 8, wherein the determination that the transition from the current position to the target position of the virtual camera collides with the three-dimensional model comprises colliding with a wall within the three-dimensional model.
 11. The method of claim 8, wherein the different navigation modes comprise a walking mode.
 12. The method of claim 8, wherein the different navigation modes comprise an orbit mode.
 13. The method of claim 8, wherein the different navigation modes comprise a floor plan mode.
 14. The method of claim 8, wherein the different navigation modes comprise a transition mode.
 15. A non-transitory computer-readable medium having instructions stored thereon that, in response to execution, cause a system including a processor to perform operations, comprising: generating a graphical user interface that facilitates viewing and navigating a three-dimensional model from different perspectives of a virtual camera in different navigation modes; receiving user input indicating a target position of the virtual camera in one of the navigation modes; in response to a determination that a transition from a current position to the target position of the virtual camera collides with the three-dimensional model: selecting a first position as a new target position, according to an algorithm, such that another transition from the current position to the first position does not collide with the three-dimensional model, and generating at least one representation of the three-dimensional model in the graphical user interface from at least one of the different perspectives based on the new target position.
 16. The non-transitory computer-readable medium of claim 15, wherein the determination that the transition from the current position to the target position of the virtual camera collides with the three-dimensional model comprises colliding with an object within the three-dimensional model.
 17. The non-transitory computer-readable medium of claim 15, wherein the determination that the transition from the current position to the target position of the virtual camera collides with the three-dimensional model comprises colliding with a wall within the three-dimensional model.
 18. The non-transitory computer-readable medium of claim 15, wherein the different navigation modes comprise a walking mode.
 19. The non-transitory computer-readable medium of claim 15, wherein the different navigation modes comprise an orbit mode.
 20. The non-transitory computer-readable medium of claim 15, wherein the different navigation modes comprise a transition mode. 